Extreme Markup Languages 2002 Montréal , Québec August 6 - 9 , 2002

Hyperdocuments present special requirements for integration with lifecycle and versioning systems. These requirements can best be summarized as "versioned linking", something not addressed by merely versioning the storage objects involved. The overriding challenge in versioned linking is resolving the correct version at the end of a link -where "correct" is defined by arbitrary business policy. This challenge can be addressed by 1) being able to precisely model a versioned hyperdocument system and 2) having rich enough versioning semantics to support the desired business policy. SnapCM is a versioning model that provides clear version and version-aware reference semantics that can be used to satisfy both of these needs. This paper presents three models that build on each other. The first is a partial object model for hyperdocuments. This first model isn't a complete hyperdocument model, but rather contains only the types and specification necessary to support the two models that follow. The second model defines a versioned hyperdocument model by extending both the first model and SnapCM. The third model extends the versioned hyperdocument model to include specifications for RTDs (Referent Tracking Documents). These models enable us to satisfy both of the versioned linking challenges. They provide well-defined support for hyperdocument lifecycle systems by describing a coherent object model to describe both the hyperdocument and SnapCM versioning domains. These models also provide rich business policy support based on SnapCM's ResolutionPolicy semantics. Rendered by www.RenderX.com Versioned Hyperdocuments Abstract Model Table of